System and method for managing entitlements to data over a network

ABSTRACT

A system and method for determining entitlement to content residing on a server. A subscriber computing device operated by a subscriber generates a request for access to a requested content residing on a content access provider server. The subscriber has an account with a multi-channel video program distributor (MVPD) and the account comprises subscription information indicative of the services provided by the MVPD to the subscriber. The content request is received by the content access provider and forwarded to an entitlements server. The entitlement determines whether the subscriber is entitled to receive the requested content based on the subscription information and sends an access granted message to the content access provider server when the subscriber is entitled to receive the requested content.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. §119(e) fromprovisional application No. 61/117,248 filed Nov. 24, 2008 and fromprovisional application No. 61/117,265 filed Nov. 24, 2008. The61/117,248 and the 61/117,265 provisional applications are incorporatedby reference herein, in its entirety, for all purposes.

BACKGROUND

Data in the form of graphics, text, video, and audio (collectively,“content”) is provided to subscribers over shared access networks. Thedata may be stored and retrieved as a file or it may be provided as avideo stream. For example video programming and live programming aretypically provided as a video stream. Cable, satellite and fibernetworks are examples of shared networks that are used to delivercontent.

Shared networks may be operated by multi-channel video programmingdistributors (MVPDs) provided to subscribers for a fee. Typically, theMVPDs obtain content from programmers. Content may be classified intiers, as for example, basic, standard and premium. The subscribersubscribes to a service package with a tier and receives the contentassociated with that tier. The subscriber may be allowed to add“premium” channels to a particular tier.

The Internet is another potential delivery mechanism of data,particularly content provided as video stream. A subscriber who obtainscontent from a particular programmer from an MVPD may desire to obtaincontent of the programmer via the Internet. This access may be providedvia a web server operated by a content access provider (CAP). Forexample, the CAP may be the content provider, a third party who hasacquired rights from a content provider, or the MVPD. Access to contentvia the Internet represents an additional revenue opportunity to MVPDand content providers.

A subscriber who is entitled to access content over a shared networkbased on an existing relationship with an MVPD is not necessarilyentitled to access the same or similar content from a CAP. At least oneimpediment to leveraging the MVPD relationship to obtain access tocontent provided by a CAP is the need to share subscriber informationbetween the MVPD and the various CAPs. Subscriber information held by anMVPD is a valuable asset of the MVPD. Subscribers also consider suchinformation as private. Thus, sharing of subscriber information held byMVPDs represents a significant deterrent to providing access toWeb-based content based on a subscriber's relationship with a MVPD.

SUMMARY

Various embodiments provide methods and systems for determining whethera subscriber is entitled to access content via an IP network based onthe subscriber's entitlement to receive the same content, relatedcontent or other content from a multi-channel video programmingdistributor without disclosing proprietary subscriber information.

DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutepart of this specification, illustrate exemplary aspects of theinvention. Together with the general description given above and thedetailed description given below, the drawings serve to explain featuresof the various embodiments.

FIG. 1 is a flow diagram illustrating a process by which a subscriber'sentitlement may be determined.

FIG. 2 is a block diagram illustrating networked components that may beused to determine a subscriber's entitlements according to anembodiment.

FIGS. 3A, B, C, and D are flow diagrams collectively a process by whichthe identity of a subscriber is provided to a content access providerusing linking according to an embodiment.

FIG. 4 is a block diagram illustrating functional components of apersonal computer.

FIG. 5 is a block diagram illustrating functional components of awireless device.

FIG. 6 is a block diagram illustrating functional components of aserver.

DETAILED DESCRIPTION

Various embodiments provide methods and systems for determining whethera subscriber is entitled to access content from a content accessprovider (CAP) via an IP network based on the subscriber's entitlementto receive the same content, related content or other content from amulti-channel video programming distributor (MVPD) and for establishinga trust relationship between the CAP and MVPD.

As used herein, the term “content” encompasses video content, audiocontent, photographic content, text content, game content, andmulti-media content. Content is sometimes collectively referred to as a“resource.”

As used herein, the term “computing device” encompasses, for example,desktop computers, laptop computers and mobile devices and otherprocessor-equipped devices that may be developed in the future that maybe configured to permit a user to interact with other devices over anetwork. As used herein, a “mobile device” encompasses cellulartelephones, personal data assistants (PDA), and smart telephones.

As used herein, a “server” is a computing device that may be configuredto interact in an automated fashion with other devices over a network toserve content and web pages, to issue responses to communications fromother network devices and to respond to queries from other networkdevices.

As previously described, certain content provided by a content accessprovider (CAP) may be provided only to subscribers who are “entitled” toreceive it. “Entitled” in this context means that a subscriber hasestablished a relationship with a multi-channel video programmingdistributor (MVPD) and that relationship entitles the subscriber toaccess designated content provided by the CAP. Various processes thatmay allow the MVPD to determine whether the subscriber is entitled toaccess the designated content may be identified herein as “entitlement”processes or determinations. In some circumstances (described in detailbelow), a subscriber may be entitled to receive content generally butmay not be authorized to receive request content at a particular time.Unless otherwise clear from the context in which the term is used,“entitled” encompasses “authorized.” Content should only be provided toa subscriber whose identity has been authenticated to an identityserver. Various processes that confirm the identity of a subscriber maybe identified herein as “authentication” or “identification” processesor determinations.

As used herein, “access to content,” encompasses viewing content,receiving content, downloading content, and acquiring content.

FIG. 1 is a flow diagram illustrating a process by which a subscriber'sentitlement to view particular content may be determined.

At block 102 subscriber requests a target resource from a content accessprovider (CAP). For example, the CAP may be the content provider, athird party who has acquired rights from a content provider, or theMVPD.

In an embodiment, the subscriber accesses the CAP via the Internet. Inthis embodiment, a subscriber that is entitled and authorized to receivecontent from the CAP may do so anywhere that an Internet connection isavailable.

At block 104, the CAP obtains a subscriber identifier (ID) from anidentity provider to authenticate the subscriber. In an embodiment, theID provider is the MVPD. In another embodiment, the identity provider isa trusted third party.

The CAP and identity provider may independently establish a relationshipwith the subscriber. In an embodiment, when both the CAP and theidentity provider have established relationships with the subscriber, asubscriber identity maintained by the identity provider and a subscriberidentity maintain by the CAP may be linked using an identifier that doesnot reveal information about the subscriber's relationship with eitherthe CAP or the identity provider. The linking of the subscriberidentities maintained by the identity provider and the CAP permits theCAP to authenticate the subscriber without redirection to the identityprovider.

Alternatively, the CAP may rely on the identity provider to authenticatethe subscriber. Optionally, when linking of identifiers is not used, anauthentication is session based and is not persistent.

At block 106, the CAP submits the subscriber ID to an entitlementdetermination process to identify the resources that the subscriber isentitled and authorized to receive. In an embodiment, the entitlementdetermination process is provided by the MVPD.

At block 108, the CAP receives that entitlement determination and grantsor denies the request for the target resource based on the entitlementsdetermination.

FIG. 2 is a block diagram illustrating the participants in the processesdescribed in FIG. 1 according to an embodiment.

A CAP server 200 comprises a content datastore 204 that is accessiblevia a network 212. In an embodiment, the network 212 is the Internet.The content datastore 204 may reside in a memory of the CAP server 200(see, FIG. 8) or it may be a separate data storage system that isaccessible to the CAP server 200. The CAP server 200 may operatesoftware applications to provide functionality to permit the CAP server200 to communicate via the network 212 and to respond to communicationsfrom other devices connected to the network 212. These applications maybe stored in a memory of the CAP server 200 (see, FIG. 8).

A subscriber computing device 208 may communicate with the CAP server200 via the network 212 to request a target resource from the contentdatastore 204. The subscriber computing device 208 may operate softwareapplications to provide functionality to permit the subscriber computingdevice 208 to communicate via the network 212 and to respond tocommunications from other devices connected to the network 212. By wayof illustration and not as a limitation, subscriber computing device 208may comprise a browser. These applications may be stored in a memory ofthe subscriber computing device 208 (see, FIGS. 6 and 7).

The CAP server 200 may communicate with the identity server 216 via thenetwork 212 to acquire a subscriber identifier for the subscriber usingthe subscriber computing device 208. The identity server 216 may operatesoftware applications to provide functionality to permit the CAP server200 to communicate via the network 212 and to respond to communicationsfrom other devices connected to the network 212. These applications maybe stored in a memory of the identity server 216 (see, FIG. 8).

In an embodiment, the subscriber computing device 208 may be redirectedto the identity server 216 to allow the subscriber using the computingdevice 208 to provide authenticating information to the identity server216.

The CAP server 200 may also communicate via the network 212 to providethe subscriber identifier to the entitlements server 220. In anembodiment, the entitlements server is under the control of the MVPDfrom which the subscriber receives services. The entitlements server 220may operate software applications to provide functionality to permit theentitlements server 220 to communicate via the network 212 and torespond to communications from other devices connected to the network212. These applications may be stored in a memory of the entitlementsserver 220 (see, FIG. 8). Additionally, the entitlements server 220 mayoperate software applications to provide functionality to permit theentitlements server 220 to interact with data storage devices andsystems of the MVPD.

The entitlements server 220 may respond to the CAP server 200 withinformation regarding the entitlements of the subscriber. Theentitlements server 220 may access subscription information in asubscriber datastore 224 to obtain sufficient information to determinethe entitlements of the subscriber.

In an embodiment, the entitlements server 220 determines a subscriber'sentitlement level for each content provider providing content to theMVPD based on information about the subscriber's subscription with theMVPD (subscription information). By way of illustration and not as alimitation, a subscriber who has paid to receive the content provider'scontent at a premium level (for example, full episodes, library content,outtakes and other extras) through an MVPD relationship (e.g., asubscription with a traditional cable or direct broadcast satelliteprovider) may be provided access to an enhanced, fully-loaded onlineexperience from the content provider's web site. Thus, the relationshipbetween the subscriber and the MVPD may permit the subscriber to accessa video stream (stored or live broadcast) through an access point, suchas a portal operated by the MVPD or the content provider. A subscriberwho has not paid for the content provider's premium content through anMVPD relationship may be routed to the content provider's standardonline experience (promotional content, limited number of full episodes,up-sell messages to subscribe to an MVPD video package).

Subscription information may include, but is not limited to subscribertier, subscriber premium services, and subscription video-on-demand(SVOD) rights. By way of illustration, video tiers include BST, CPST,Digital, among others. Premium video services may include HBO, SHO,Starz, and SVOD rights may include movies on demand and access to payper view events.

The CAP server 200 may use the entitlements information provided by theentitlements server 220 to determine whether to grant or deny therequest for a target resource.

In another embodiment, the entitlements server 220 may track andreconcile any differences across divisions related to which networks areincluded in which tiers and packages. The entitlements server 220 alsoconfirms that all broadcast network stations are consistently includedin all video programming tiers, across all divisions and regions of theMVPD. The entitlements server 220 also confirms that those cable networkstations are consistently included in all video programming tiers aboveBST across all divisions and regions of the MVPD. The entitlementsserver 220 further confirms that any bundled multiplex premium serviceentitlement subscriptions are included with their corresponding premiumservice entitlements. The entitlements server 220 additionally confirmsthat, where appropriate, all bundled SVOD subscriptions are includedwith their corresponding premium service entitlements.

In an embodiment, the subscriber identifier is written to the subscribercomputing device 208 used by the subscriber to access the CAP server200. In this embodiment, the subscriber identifier may remain active andavailable to the CAP server 200 on that subscriber's computing device208 (by means of a cookie or other unobtrusive technology placed onsubscriber's computing device 208 by the CAP server 208), so that futureattempts to access the content from the CAP do not require customerlog-in or re-registration (assuming cookie is still in place onsubscriber's computing device).

In an embodiment, the entitlements server 216 provides the contentprovider either a positive or negative response to the question: “Isthis subscriber entitled to view the CAP's content as part of his/hersubscription service?” The entitlements server 216 may interface withvarious system of the MVPD to determine a subscriber's entitlement levelfor each content provider providing content to the MVPD. In thisembodiment, the CAP server 200 writes the subscriber's entitlementstatus for its content to the subscriber's computing device (by means ofa second cookie or other unobtrusive technology placed on subscriber'saccess device by the CAP server). In an embodiment, the entitlementstatus information is valid for a pre-determined time as agreed to bythe CAP and the MVPD.

In embodiment, the entitlement status (as stored on cookie or othermeans used by the CAP) may be updated by the CAP's system withoutrequiring the subscriber to log in or re-register.

In another embodiment, the entitlement status of a subscriber isdetermined using a message exchange the does not require cookies orother persistent information to be stored on the subscriber computingdevice 208.

In an embodiment, the CAP and the MVPD utilize a single sign on (SSO)solution that permits a subscriber to establish sessions with bothparties by presenting credentials only once. The SSO solution may beimplemented using linked identities where the CAP and MVPD each maintainseparate identities for a subscriber. In an embodiment, the identitiesare linked in accordance with Security Assertion Markup Language (SAML)v2.0 standards promulgated by the Organization for the Advancement ofStructured Information Standards (“OASIS”).

In a non-linking environment, the CAP implements a federated model usingSAML 2.0 to perform the authentication. When a subscriber attempts toaccess secure content from the CAP server 200, the CAP will make arequest to the identity server 216 via the subscriber computing device208. A response from the identity server 216 will contain thesubscriber's identifier (GUID). The CAP will then make a request to theentitlements server 220 to obtain the entitlements for the subscriber.

In a linking environment, the CAP implements a federated model usingSAML 2.0 to perform the authentication. When a subscriber attempts toaccess secure content from the CAP server 200, the CAP server 200 willmake a request to the identity server 216 to check whether thesubscriber has an authentication session. If needed the CAP will requirelogin and check for an association to a MVPD and check the entitlementlevels. If no association is present then the CAP will request that thesubscriber link his or her CAP identity with the subscriber's MVPDidentity. The response from the identity server 216 will contain thesubscriber's ID (GUID) and a pseudonym for linking the identities. TheCAP will then store the pseudonym along with the GUID for thissubscriber in the persistent profile. The CAP will then make a requestto the entitlements server 220 to obtain the entitlements for thesubscriber using the GUID.

FIGS. 3A-D collectively illustrate a flow of an entitlement confirmationprocess according to embodiments. FIG. 3A illustrates the overall flowof the entitlements confirmation process while FIGS. 3C-3D illustrateadditional processes that may be required to complete the entitlementconfirmation process.

Referring to FIG. 3A, a subscriber requests content for a CAP (block502). The CAP server determines whether the content requires that thesubscriber be “entitled” to view the content (block 504). If entitlementis not required (i.e., if decision 504 is “No”), the subscriber is shownthe requested content (block 506). If entitlement is required (i.e., ifdecision 504 is “Yes”), the CAP server determines whether the subscriberis already logged in to the CAP server domain (block 508). If thesubscriber is not logged in to the CAP server domain (i.e., if decision508 is “No”), the subscriber is authenticated to the CAP server bylogging in (block 510) with credentials accepted by the CAP server. Ifthe subscriber is logged in (i.e., if decision 508 is “Yes”), or afterthe subscriber logs in (block 510), the CAP server determines whetherthe subscriber has linked an identity between the subscriber and an MVPDand an identity between the subscriber and the CAP server (block 512).

If the subscriber is not linked (i.e., the decision 512 is “No”), theprocess branches to a linking process as indicated by reference “E.”This linking process is described below in reference to FIG. 3B. If thesubscriber is linked (i.e., the decision 512 is “Yes”), or after thelinking process is completed and the identities are linked (indicated byreturn reference “F”), the CAP server sends an entitlement request tothe entitlements server (block 514). In an embodiment, the entitlementsrequest comprises an identifier associated with the subscriber that isknown to the entitlements server and that links the identity between thesubscriber and an MVPD and an identity between the subscriber and theCAP server. In this embodiment, the identifier may be distinct from anidentifier assigned by the CAP server and an identifier assigned by theMVPD. By way of illustration and not by way of limitation, theidentifier provided in the entitlements request may be a global uniqueId (GUID). The entitlements request and the identifier are received bythe entitlements server (block 516).

The process branches to an entitlement determination process asindicated by reference “A.” This entitlements determination process isdescribed below in reference to FIG. 3D. After the entitlementsdetermination process is completed (indicated by return reference “B”),the entitlements server sends a response to the entitlements request tothe CAP server (block 518).

The CAP server determines from the response whether the subscriber isentitled to access the requested content (block 520). If the subscriberis entitled to access the requested content (i.e., the decision 520 is“Yes”), the user is provided access to the content (block 522). If thesubscriber is not entitled to access the requested content (i.e., thedecision 520 is “No”), the user is denied access to the content (block522).

As discussed above, the CAP server determines whether the subscriber haslinked an identity between the subscriber and an MVPD and an identitybetween the subscriber and the CAP server (block 512). If the subscriberis not linked (i.e., the decision 512 is “No”), the process branches toa linking process as indicated by reference “E.” Referring to FIG. 3B, alinking process commences with the CAP server redirecting the subscribercomputing device to a linking page (block 530). The subscriber computingdevice displays a linking page from the CAP server (block 532). The pagealso queries the subscriber to select the subscribers MVPD (block 536).The subscriber computing device sends a linking request to the CAPserver (block 538).

The CAP server receives the linking request and sends an authenticationrequest to the identity provider server of the selected MVPD (block540). In an embodiment, the identity provider of the selected MVPD isthe MPVD. In another embodiment, the identity provider is a third partythat provides identity services to the MVPD.

The identity provider server receives the authentication request anddetermines whether the subscriber is currently logged in to the identityprovider domain (block 542). If the subscriber is not logged in (i.e.,the decision 542 is “No”), the identity provider server queries thesubscriber computing device to determine if the subscriber is currentlyregistered with the identity provider (block 544). If the subscriber isnot registered (i.e., the decision 544 is “No”), the process branches toa registration process as indicated by reference “K.” If the subscriberis currently registered (i.e., the decision 544 is “Yes”), thesubscriber computing device queries the subscriber for login credentialsaccepted by the identity provider (block 546).

The credentials are sent to the identity provider server forverification (block 547). If the subscriber credentials are not verified(i.e., the decision 547 is “No”), the identity provider server againqueries the subscriber for the login credentials (block 546). If thesubscriber credentials are verified (i.e., the decision 544 is “Yes”),or if the subscriber was currently logged in (i.e., the decision 542 is“Yes”), the identity provider server sends a redirect to the subscribercomputing device to the subscriber computing device (block 548).

The subscriber computing device displays the link confirmation page 550.The identity provider server sends a SAML2 assertion to the CAP server(block 552). The CAP server receives the assertion and redirects thesubscriber computing device to a CAP login and linking page (block 554).The subscriber computing device receives the CAP credentials required tolink the accounts and provides the linking credentials to the CAP server(block 556). The CAP server then links the accounts (block 558). Theaccount linking process returns to the overall flow of the entitlementsconfirmation process illustrated in FIG. 3A as indicated by reference“F.”

As discussed above, the identity provider server queries the subscribercomputing device to determine if the subscriber is currently registeredwith the entitlements server (block 544). If the subscriber is notregistered (i.e., the decision 544 is “No”), the process branches to aregistration process as indicated by reference “K.” Referring to FIG.3C, a registration process commences with the subscriber computingdevice displaying a query whether the subscriber desires to registerwith the entitlements server (block, 560). As previously described, asubscriber of a MVPD may have a subscriber identity with the MVPD. Inaddition, to use the entitlement confirmation process, the subscribermay require an identity that relates to the subscriber's identity withthe MVPD but does not permit access to the subscriber's account orreveal information about the subscriber or the subscriber's account. Byway of illustration and not by way of limitation, the identifierprovided in the entitlements request may be a global unique Id (GUID).

To register the subscriber with the entitlements server, the subscribercomputing device sends a registration request to an authenticationserver (block 560). The authentication server receives the registrationrequest and returns a registration page to the subscriber computingdevice (block 562). The subscriber computing device receives theregistration information from the subscriber and sends the informationto the an authentication server (block 564). The authentication servercreates an identity for the subscriber and redirects the subscriber tothe CAP's account linking process (block 566) as indicated by reference“G” (see, FIG. 3B). Referring to FIG. 3B, the CAP server sends anauthenticate request to the identity provider of the selected MVPD(block 540).

As discussed in reference to FIG. 3A, an entitlements request isforwarded from the CAP server to the entitlements server (block 516). Inan embodiment, the entitlement request includes the IP address of thesubscriber computing device from which the request originates. Theprocess branches to an entitlements determination process as indicatedby reference “A.” Referring to FIG. 3D, the entitlements server maycheck the number of IP addresses associated with the subscriberidentifier (block 570). The entitlements server determines whether thenumber of addresses associated with the subscriber at any one time isless than or equal to a maximum allowed number of simultaneous addresses(block 572). Setting a maximum number of IP address permits a CAP and/orthe MVPD to allow sessions to be established by a subscriber frommultiple locations. For example, a household may desire tosimultaneously access different content from a CAP server from differentlocations (e.g., home, school, office, hot-spot, and vacation home). Thehousehold may be permitted up to a predetermined maximum number ofsimultaneous IP addresses to be associated with a subscriber identifierto manage capacity on the entitlements server and/or the CAP server andto prevent account abuse. In an embodiment, the maximum number of IPaddresses allowed for a particular subscriber identifier may depend onthe level of service that the subscriber has subscribed to or any otherbusiness rule the entitlements server imposes.

In an embodiment, the maximum allowed number of simultaneous unique IPaddresses may be established over a period of time. For example, if inthe last “X” hours there are more than “Y” entitlement requests for aparticular subscriber identifier with unique IP addresses, the nextrequest invoking the subscriber identifier may not be authorized.

In another embodiment, each time a subscriber logs into a CAP serversends and makes a request for content that requires entitlement the CAPserver forwards an entitlement request to the entitlements server. Theentitlement server determines whether the subscriber is entitled to therequested content and whether the subscriber is authorized to receiveit. If both of these determinations are decided in the affirmative, asession is established between the subscriber computing device fromwhich the request originated and the CAP server. Because a subscriberidentity may be shared by a household, multiple simultaneous sessionsmay be established with a CAP using a single subscriber identifier. Inorder to prevent abuse (e.g., where the subscriber identity is sharedwith non-household members), a CAP may impose a maximum number ofsessions and/or streams associated with a particular subscriberidentifier.

In an embodiment, the entitlement response may include an expirationtime. In this embodiment, the CAP checks the checks the status of theentitlement response. If the response has not expired, additionalcontent requests that are consistent with the entitlement response maybe granted by the CAP server without making an entitlement request tothe entitlement server.

Returning to FIG. 3D, if the number of concurrent IP addresses isgreater than or equal to the maximum allowed sessions (i.e., decision572 is “Yes”), a decision to deny access is made and a “deny” responseis returned (block 594) as indicated by reference “B” (see also, FIG.3A). If the number of concurrent sessions is less than the maximumallowed sessions (i.e., decision 572 is “No”), a request is sent to anenterprise identity server to search for the subscriber account numberusing the subscriber identifier, and the results are returned to theentitlements server (block 582).

The entitlements server determines whether the subscriber account numberwas found (block 580). If the subscriber account number is not found(i.e., decision 572 is “No”), a decision to deny access is made and a“deny” response is returned (block 594) as indicated by reference “B”(see also, FIG. 3A). If the subscriber account number is found (i.e.,decision 572 is “Yes”), subscription information for the subscriber isobtained and the program channels which the subscriber is authorized toreceive are identified and reported to the entitlements server (block582).

The entitlements server applies business policies to the subscriptioninformation to determine whether to allow the subscriber to access therequested content (block 584). As illustrated in FIG. 3D, the accountstatus (block 586) and the account delinquency (block 588) are checked.However, this not meant to be a limitation. Other business policies maybe applied to the determine whether to allow the subscriber to accessthe requested content. By way of illustration and not as a limitation,the account may be checked for the age of the account, for the paymenthistory on the account, and whether the account has been associated withundesirable conduct (abuse of equipment, abuse of bandwidth, forexample).

If the account is determined to be inactive (i.e., decision 586 is“No”), a decision to deny access is made and a “deny” response isreturned (block 594) as indicated by reference “B” (see also, FIG. 3A).If the subscriber account number is determined to be active (i.e.,decision 586 is “Yes”), a decision is made whether the account isdelinquent (block 588). If the account is determined to be delinquent(i.e., decision 588 is “Yes”), a decision to deny access is made and a“deny” response is returned (block 594) as indicated by reference “B”(see also, FIG. 3A). If the account is determined to be current (i.e.,decision 588 is “No”), account and programmer content policies areapplied to the subscription information to determine the channels of theCAP which the subscriber is entitled to received from the MVPD (block590). By way of illustration and not by way of limitation, the premiumand non-premium channels that are included in the subscription of thesubscriber may be identified and the entitlements of the subscriber tocontent provided by the CAP may be determined.

The requested content is reviewed against the entitlements of thesubscriber (block 592). If the requested content is not authorized(i.e., decision 592 is “No”), a decision to deny access is made and a“deny” response is returned (block 594) as indicated by reference “B”(see also, FIG. 3A). If the requested content is authorized (i.e.,decision 592 is “Yes”), a decision to permit access is made and a“permit” response is returned (block 594) as indicated by reference “B”(see also, FIG. 3A).

In an embodiment, the IP address of the subscriber computing device isused to search a datastore for a related modem. A determination is madewhether the related modem is found. If a related modem is found, the IPaddress is identified as “on-net.” If a related modem is not found, theIP address is identified as “off-net.” In an embodiment, theon-net/off-net status may be used to determine whether a subscriber isentitled to view particular content. In another embodiment, theon-net/off-net status may be incorporated into a business policy andapplied to subscriber information to determine a subscriber'sentitlement to view particular content (block 584). In yet anotherembodiment, the MVPD may offer improved quality-of-service (QoS) forcontent packets that delivered “on-net.” The improved QoS may be afunction of the service level of the subscriber or offered as a premiumupgrade.

The entitlements process illustrated in FIGS. 3A-D anticipates that boththe CAP and the identity provider server maintain identities forsubscribers and that these identities may be linked. However, thesefigures and the description that follows are illustrative only and arenot limiting. As described above, when the CAP does not maintain anidentity for subscribers the subscriber may be authenticated by theidentity provider server and the entitlements process is adaptedaccordingly.

In another embodiment, the MVPD proxies the CAP. In this embodiment, allcontent may be deemed “on-net” and QoS attribute applied to delivery ofthat content.

The entitlement process illustrated in FIGS. 3A-D contemplates asubscriber ID that is not present on the subscriber computing device. Inan embodiment, a customer entitlement identifier (subscriber identifier)is stored on the subscriber computing device and reflects theentitlements of a subscriber. By way of the illustration and not as alimitation, the subscriber identifier may be in the form of a cookie.

In an embodiment, the cookie may be to convey a subscriber identifier tothe CAP server. The CAP server may then use the subscriber identifierfrom the cookie to search a CAP subscriber database to confirm that thesubscriber is registered with the CAP.

In an embodiment, the entitlements system is updated and kept currentaccording to a schedule. The following exemplary schedule is provided toillustrate this embodiment and is not meant as a limitation:

Service information related to video tiers (BST, CPST, Digital) isupdated on a daily basis.

Service information related to all premium video services is updated ona daily basis.

Service information related to Subscription Video On Demand (SVOD)services is updated on a daily basis.

Service information related to transactional Video On Demand (VOD)services is updated on an immediate basis.

As previously described, the subscriber may interact with the variousservers and network components using a variety of the computing devices,including a personal computer. By way of illustration, the functionalcomponents of a personal computer 760 are illustrated in FIG. 4. Such apersonal computer 760 typically includes a processor 761 coupled tovolatile memory 762 and a large capacity nonvolatile memory, such as adisk drive 763. The computer 760 may also include a floppy disc drive764 and a compact disc (CD) drive 765 coupled to the processor 761.Typically the computer device 760 will also include a pointing devicesuch as a mouse 767, a user input device such as a keyboard 768 and adisplay 769. The computer device 760 may also include a number ofconnector ports coupled to the processor 761 for establishing dataconnections or receiving external memory devices, such as a USB orFireWire® connector sockets or other network connection circuits 766 forcoupling the processor 761 to a network. In a notebook configuration,the computer housing includes the pointing device 767, keyboard 768 andthe display 769 as is well known in the computer arts.

While the capability of the subscriber computing device 208 (see, FIG.2) has been disclosed with respect to a computer, those skilled in theart will also appreciate that the system can be embodied in a mannerthat utilizes mobile devices. For example, cell phones, PDA's and othermobile devices may perform some or all of the functions of subscribercomputing device 208.

Typical mobile devices suitable for use with the various embodimentswill have in common the components illustrated in FIG. 5. For example,the exemplary mobile device 890 may include a processor 891 coupled tointernal memory 892, a display 893 and to a SIM 899 or similar removablememory unit. Additionally, the mobile device 890 may have an antenna 894for sending and receiving electromagnetic radiation that is connected toa wireless data link and/or cellular telephone transceiver 895 coupledto the processor 891. In some implementations, the transceiver 895 andportions of the processor 891 and memory 892 used for cellular telephonecommunications are collectively referred to as the air interface sinceit provides a data interface via a wireless data link. Mobile devicestypically also include a key pad 896 or miniature keyboard and menuselection buttons or rocker switches 897 for receiving user inputs.

The processor 891 may be any programmable microprocessor, microcomputeror multiple processor chip or chips that can be configured by softwareinstructions (applications) to perform a variety of functions, includingthe functions of the various embodiments described herein. In somemobile devices, multiple processors 891 may be provided, such as oneprocessor dedicated to wireless communication functions and oneprocessor dedicated to running other applications. Typically, softwareapplications may be stored in the internal memory 892 before they areaccessed and loaded into the processor 891. In some mobile devices, theprocessor 891 may include internal memory sufficient to store theapplication software instructions. The internal memory of the processormay include a secure memory 898 which is not directly accessible byusers or applications and that is capable of recording MDINs and SIM IDsas described in the various embodiments. As part of the processor, sucha secure memory 898 may not be replaced or accessed without damaging orreplacing the processor. In some mobile devices, additional memory chips(e.g., a Secure Data (SD) card) may be plugged into the device 890 andcoupled to the processor 891. In many mobile devices, the internalmemory 892 may be a volatile or nonvolatile memory, such as flashmemory, or a mixture of both. For the purposes of this description, ageneral reference to memory refers to all memory accessible by theprocessor 891, including internal memory 892, removable memory pluggedinto the mobile device, and memory within the processor 891 itself,including the secure memory 898.

A number of the aspects described above may also be implemented with anyof a variety of remote server devices, such as the server 900illustrated in FIG. 6. Such a server 900 typically includes a processor901 coupled to volatile memory 902 and a large capacity nonvolatilememory, such as a disk drive 903. The server 900 may also include afloppy disk drive and/or a compact disc (CD) drive 906 coupled to theprocessor 901. The server 900 may also include a number of connectorports 904 coupled to the processor 901 for establishing data connectionswith network circuits 905.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the steps of the various embodiments must be performed inthe order presented. As will be appreciated by one of skill in the artthe order of steps in the foregoing embodiments may be performed in anyorder. Further, words such as “thereafter,” “then,” “next,” etc. are notintended to limit the order of the steps; these words are simply used toguide the reader through the description of the methods.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with the aspectsdisclosed herein may be implemented or performed with a general purposeprocessor, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor maybe a microprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of the computingdevices, e.g., a combination of a DSP and a microprocessor, a pluralityof microprocessors, one or more microprocessors in conjunction with aDSP core, or any other such configuration. Alternatively, some steps ormethods may be performed by circuitry that is specific to a givenfunction.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. The steps of a method or algorithm disclosedherein may be embodied in a processor-executable software module whichmay reside on a computer-readable medium. Computer-readable mediaincludes both computer storage media and communication media includingany medium that facilitates transfer of a computer program from oneplace to another. A storage media may be any available media that may beaccessed by a computer. By way of example, and not limitation, suchcomputer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disc storage, magnetic disk storage or other magnetic storagedevices, or any other medium that may be used to carry or store desiredprogram code in the form of instructions or data structures and that maybe accessed by a computer.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such asinfrared, radio, and microwave, then the coaxial cable, fiber opticcable, twisted pair, DSL, or wireless technologies such as infrared,radio, and microwave are included in the definition of medium. Disk anddisc, as used herein, includes compact disc (CD), laser disc, opticaldisc, digital versatile disc (DVD), floppy disk, and blu-ray disc wheredisks usually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of computer-readable media. Additionally, theoperations of a method or algorithm may reside as one or any combinationor set of codes and/or instructions on a machine readable medium and/orcomputer-readable medium, which may be incorporated into a computerprogram product.

The preceding description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentinvention. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thescope of the invention. Thus, the present invention is not intended tobe limited to the embodiments shown herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein. Further, any reference to claim elements in the singular, forexample, using the articles “a,” “an,” or “the,” is not to be construedas limiting the element to the singular.

1. A method for determining entitlement to content residing on a servercomprising: associating a subscriber identifier with an account of asubscriber with a content access provider, wherein the subscriberidentifier is associated with an account of the subscriber with amulti-channel video program distributor (MVPD) and wherein the accountwith the MVPD comprises a subscription level indicative of servicesprovided by the MVPD to the subscriber; receiving a request from asubscriber computing device operated by the subscriber for access to arequested content provided by a content provider residing on a contentaccess provider server; authenticating the subscriber at the contentaccess provider server using credentials accepted by the content accessprovider to obtain the subscriber identifier; forwarding the contentrequest and the subscriber identifier from the content access providerserver to an entitlements server; determining by the entitlements serverusing the subscriber identifier the subscription level of the subscriberassociated with the subscriber's account with the MVPD; determining bythe entitlement server from the subscription level whether thesubscriber is entitled to receive qualifying services of the contentprovider from the MVPD; and authorizing by the entitlements serveraccess to the requested content on the content access provider serverwhen the subscriber is entitled to receive qualifying services of thecontent provider from the MVPD.
 2. The method of claim 1, wherein thecontent is selected from the group consisting of video content, audiocontent, photographic content, text content, game content, andmulti-media content.
 3. The method of claim 1, wherein the subscribercomputing device is selected from the group consisting of a desktopcomputer, a laptop computer, a mobile device, a PDA, and a cell phone.4. The method of claim 1, wherein the content access server and thesubscriber computing device communicate via a network.
 5. The method ofclaim 4, wherein the network is selected from the group consisting of awired network, a wireless network, a public switched network, a packetswitched network, a hybrid-fiber coax network, a fiber network, and asatellite network.
 6. The method of claim 1, wherein determining by theentitlement server from the subscription level whether the subscriber isentitled to receive qualifying services of the content provider from theMVPD comprises: identifying from the subscription level one or morechannels that the subscriber is entitled to receive from the MVPD; anddetermining whether the entitlement to receive the one or more channelsis a qualifying service that entitles the subscriber to access therequested content.
 7. The method of claim 1, wherein the subscriptionlevel is selected from the group consisting of a list of subscribedchannels, a service package descriptor indicative of a subscribed levelof service, and a list of subscribed premium services.
 8. The method ofclaim 1, wherein the services provided by the MVPD are broadcasted overa shared network.
 9. The method of claim 8, wherein the shared networkis selected from the group consisting of a shared cable network, ashared hybrid-fiber-coax network, a shared fiber network, a sharedsatellite network, and a shared IP network.
 10. A system for determiningentitlement to content residing on a server comprising: a content accessprovider server comprising a first processor; an entitlements servercomprising a second processor, wherein: the first processor isconfigured with software executable instructions to cause the contentaccess provider server to perform operations comprising: associating asubscriber identifier with an account of a subscriber with a contentaccess provider, wherein the subscriber identifier is associated with anaccount of the subscriber with a multi-channel video program distributor(MVPD) and wherein the account with the MVPD comprises a subscriptionlevel indicative of services provided by the MVPD to the subscriber;receiving a request from a subscriber computing device operated by asubscriber for access to a requested content provided by a contentprovider and residing on the content access provider server;authenticating the subscriber at the content access provider serverusing credentials accepted by the content access provider to obtain thesubscriber identifier; forwarding the content request and the subscriberidentifier from the content access provider server to the entitlementsserver, and the second processor is configured with software executableinstructions to cause the entitlements server to perform operationscomprising: determining using the subscriber identifier the subscriptionlevel of the subscriber associated with the subscriber's account withthe MVPD; determining from the subscription level whether the subscriberis entitled to receive qualifying services of the content provider fromthe MVPD; and authorizing access to the requested content on the contentaccess provider server when the subscriber is entitled to receivequalifying services of the content provider from the MVPD.
 11. Thesystem of claim 10, wherein the content is selected from the groupconsisting of video content, audio content, photographic content, textcontent, game content, and multi-media content.
 12. The system of claim10, wherein the subscriber computing device is selected from the groupconsisting of a desktop computer, a laptop computer, a mobile device, aPDA, and a cell phone.
 13. The system of claim 10, wherein thesubscriber computing device and the content access provider servercommunicate via a network selected from the group consisting of a wirednetwork, a wireless network, a public switched network, a packetswitched network, a hybrid-fiber coax network, a fiber network, and asatellite network.
 14. The system of claim 10, wherein the instructionfor determining from the subscription level whether the subscriber isentitled to receive qualifying services of the content provider from theMVPD comprises: identifying from the subscription level one or morechannels that the subscriber is entitled to receive from the MVPD; anddetermining whether the entitlement to receive the one or more channelsis a qualifying service that entitles the subscriber to access therequested content.
 15. The system of claim 10, wherein the subscriptionlevel is selected from the group consisting of a list of subscribedchannels, a service package descriptor indicative of a subscribed levelof service, and a list of subscribed premium services.
 16. The system ofclaim 10, wherein the services provided by the MVPD are broadcasted overa shared network.
 17. The system of claim 16, wherein the shared networkis selected from the group consisting of a shared cable network, ashared hybrid-fiber-coax network, a shared fiber network, a sharedsatellite network, and a shared IP network.